't showing the
error, so something else in the document is causing it:
\setvalue{W3}{this is text for W3}
\defineregister[learnedshort][compress=yes]
\setupregister[learnedshort][style=sansbold, textstyle=slanted, n=3,
pagenumber=yes, indicator=no]
%
\defineregister[learnedlong][compress=yes]
\set
the
error, so something else in the document is causing it:
\setvalue{W3}{this is text for W3}
\defineregister[learnedshort][compress=yes]
\setupregister[learnedshort][style=sansbold, textstyle=slanted, n=3,
pagenumber=yes, indicator=no]
%
\defineregister[learnedlong][compress=yes]
\set
}
\defineregister[learnedshort][compress=yes]
\setupregister[learnedshort][style=sansbold, textstyle=slanted, n=3,
pagenumber=yes, indicator=no]
%
\defineregister[learnedlong][compress=yes]
\setupregister[learnedlong][style=sansbold, textstyle=slanted, n=2,
pagenumber=yes, indicator=no]
%
\define[1
{\glyphslant 500 test \glyphslant \numericscaled2.0\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
The problem is that compact mode uses them to apply the slanted feature
without any manual use of the commands from a user
\glyphslant
test} test
test {\glyphweight 100 test \glyphweight\numericscaled2.0\glyphweight
test} test
\stoptext
The problem is that compact mode uses them to apply the slanted feature
without any manual use of the commands from a user.
\enableexperiments[fonts.compact]
\definefontfamily
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 19:39:
On 3/8/24 19:09, Wolfgang Schuster wrote:
Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
[...]
LMTX gets b, c and d in slanted form.
LuaTeX gets only b and c in slanted form.
[...]
I get b and d in italic which
On 3/8/24 19:09, Wolfgang Schuster wrote:
> Pablo Rodriguez via ntg-context schrieb am 08.03.2024 um 18:50:
>> [...]
>> LMTX gets b, c and d in slanted form.
>>
>> LuaTeX gets only b and c in slanted form.
> [...]
> I get b and d in italic which is the expected out
},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
},
it={style: regular, features:{default, quality, slanted}},
sl={style: regular, features:{default, quality, slanted}}]
\setupbodyfontenvironment
[default]
[em=italic]
\setupbodyfont[mainface]
\starttext
\startTEXpage[offset=1em]
a\\
\em b\\
\em c\\
\em d
Dear list,
the following latest gets differents results when compiled with MkXL and
MkIV (in current latest from 2024.03.05 11:26):
\definefontfamily[mainface][rm][TeX Gyre Termes]
[features={default, quality},
it={style: regular, features:{default, quality, slanted}},
sl={style
On 3/3/2024 11:54 AM, Pablo Rodriguez via ntg-context wrote:
Dear list,
I have the following sample:
\definefontfeature[wider][extend=2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[features={default, quality, wider},
it={style: regular, features:{default, slanted
Dear list,
I have the following sample:
\definefontfeature[wider][extend=2]
\definefontfamily[mainface][rm][TeX Gyre Pagella]
[features={default, quality, wider},
it={style: regular, features:{default, slanted, quality}},
bf={style: regular, features:{default, boldened-30
2/2024 à 18:34, Henning Hraban Ramm a écrit :
> > Am 28.02.24 um 08:34 schrieb Otared Kavian:
> >> Dear Dalyoung,
> >>
> >> Thank you very much for your insight. I downloaded the Noto Serif JP
> >> fonts and set up a fontfamily as you indicated, by adding
>
a fontfamily as you indicated, by adding
> >> \setscript[nihongo]
> >> which solves a problem I had with line breakings. And everything
> >> works smoothly!
> >>
> >> So, for the mail archive, here is what I have and what works fine:
> >>
> >
works fine:
%%% Noto Fonts
\definefontfamily[JapaneseFont][rm][Noto Serif JP]
[ it={style:regular,features:{*,slanted}},
sl={style:regular,features:{*,slanted}},
bi={style:bold,features:{*,slanted}},force=yes]
\definefontfamily[JapaneseFont][ss][Noto Serif JP
, for the mail archive, here is what I have and what works fine:
%%% Noto Fonts
\definefontfamily[JapaneseFont][rm][Noto Serif JP]
[ it={style:regular,features:{*,slanted}},
sl={style:regular,features:{*,slanted}},
bi={style:bold,features:{*,slanted}},force=yes
and what works fine:
%%% Noto Fonts
\definefontfamily[JapaneseFont][rm][Noto Serif JP]
[ it={style:regular,features:{*,slanted}},
sl={style:regular,features:{*,slanted}},
bi={style:bold,features:{*,slanted}},force=yes]
\definefontfamily[JapaneseFont][ss][Noto Serif JP
;Noto Serif CJK KR” to Japanese font.
I also use "\setscript[hangul]” when I use Korean as mainlanaguage.
I hope that you may enhance the following code.
Best regards,
Dalyoung
%%% Noto Fonts
\definefontfamily[notoFont][rm][Noto Serif CJK KR]
[ it={style:regular,features:{*,slanted}}
,
]
\starttext
\startchapter [title={Oops!}]
\input knuth-gpt \par
\stopchapter
\stoptext
Replacing the textstyle /cap/ by any of /bold/, /slanted/, /smallcaps/,
and /italic/ results in a clean compilation but the indicated style is
not applied. Using a style
dth and/or a
general slant trough `currenttransform := identity slanted ...`[3] and/or
modifying heights, and the conversion method may be less sophisticated
(though it avoided needing to remove overlaps!) but still! I have often
thought about doing a more ambitious project using more metaness
On 9/2/23 12:42, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 02.09.2023 um 12:35:
>> [...]
>> Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
>> know I should know better, but I‘m stuck at this):
>>
>> \definefontfamily[mai
Pablo Rodriguez schrieb am 02.09.2023 um 12:35:
[...]
Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
know I should know better, but I‘m stuck at this):
\definefontfamily[mainface][rm][DejaVu Sans]
[sl≃style:bf]
You're using the wrong symbol (you have a math
same output as I get with MkIV, the slant stays
> the same for all sizes.
This works also perfectly fine for me now.
Many thanks for the fix and the help, Hans and Wolfgang.
Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I
know I should know better, but I‘m stuck at t
][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX
:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
\startTEXpage
a {\em b}
\stopTEXpage
\startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
a {\em b}
\stopTEXpage
\stoptext
Using LMTX higher font size gives less slanted text
Pablo Rodriguez schrieb am 02.09.2023 um 10:25:
Dear list,
I have the following sample (using current latest from 2023.08.27 13:48):
\setupinteractionscreen[option=max]
\definefontfamily[maf][rm][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt
Dear list,
I have the following sample (using current latest from 2023.08.27 13:48):
\setupinteractionscreen[option=max]
\definefontfamily[maf][rm][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
\setupbodyfont[maf, 8pt]
\setupfittingpage[offset=1ex]
\starttext
in the document.
Ah, yes (and a similar point can be made about slanted/oblique (\sl). Many
thanks for the clarification.
Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
.
ConTeXt has a command which can be used to check whether the current
active font provides the smcp feature but the recommended way is to
choose a font which supports to method (\sc or \setsmallcaps) which is
used in the document.
Ah, yes (and a similar point can be made about slanted/oblique (\sl
%
> \defineregister[learnedshort][compress=yes]
> \setupregister[learnedshort][style=sansbold, textstyle=slanted, n=2,
> pagenumber=yes, indicator=no] %
> \defineregister[learnedlong][compress=yes]
> \setupregister[learnedlong][style=sansbold, textstyle=slanted, n=2,
> pagenumber=yes, i
his custom index using this code, in both the textbook and
> workbook: %
> \defineregister[learnedshort][compress=yes]
> \setupregister[learnedshort][style=sansbold, textstyle=slanted, n=2,
> pagenumber=yes, indicator=no] %
> \defineregister[learnedlong][compress=yes]
> \setupre
:
> I am making a textbook and workbook set.
> I have this custom index using this code, in both the textbook and
> workbook: %
> \defineregister[learnedshort][compress=yes]
> \setupregister[learnedshort][style=sansbold, textstyle=slanted, n=2,
> pagenumber=yes, indicator=no] %
I am making a textbook and workbook set.
I have this custom index using this code, in both the textbook and workbook:
%
\defineregister[learnedshort][compress=yes]
\setupregister[learnedshort][style=sansbold, textstyle=slanted, n=2,
pagenumber=yes, indicator=no]
%
\defineregister[learnedlong
][name:LucidaBright-Demi]
\definefontsynonym[SerifBoldItalic][name:LucidaBright-DemiItalic]
\definefontsynonym[SerifSlanted][name:LucidaBright-Slanted]
\definefontsynonym[SerifCaps][name:LucidaBrightSmallcaps]
\definefontsynonym[SerifBoldCaps][name:LucidaBrightSmallCaps-Demi]
\stoptypescript
\getvalue{} is placed inside, it can't find the value.
Any suggestions?
--Joel
\defineregister[coreidea][compress=yes]\setupregister[coreidea][style=sansbold,
textstyle=slanted, n=2, pagenumber=yes, indicator=no]
\define[1]\setcoreidea{%
\coreidea{#1}%
}
\setvalue{secret1}{this won't work
xclamation
marks, so they are at the same height that its closing counterparts.
I thought there may be a GPOS feature that could achieve this, but I
must admit I have no idea about how to achive it.
In my document, this should only work with the slanted feature.
Could anyone tell me how could I move vertically
there may be a GPOS feature that could achieve this, but I
must admit I have no idea about how to achive it.
In my document, this should only work with the slanted feature.
Could anyone tell me how could I move vertically single glyphs?
Many thanks f
I get a decidedly odd (or, at least, unexpected by me) result from this, based
on the example on the contextgarden page for definestartstop:
\starttext
\defineblank[ExtractDistance][3pt]
\definestartstop[Extract][
style=slanted,
before={\blank[ExtractDistance]
\setupnarrower[left
nice:
https://gitlab.com/smc/fonts/Nupuram/-/blob/master/docs/README.md
which is used like:
\startTEXpage[offset=1dk,align={normal,tolerant,stretch}]
\definefontfeature[colored][default][colr=9]
\definefontfeature[slanted][default][slant=.2]
\definedfont[name:nupuramregular*default
with Japanese in
LMTX (on macOS).
1. You need a font to typeset japanese.
2. Add \setscript[nihongo] to your document to enable line breaks.
begin example
\definefontfamily [noto-cjk-jp] [serif] [Noto Serif CJK JP]
[it={style:regular,features:{*,slanted}},
bi={style:bold,features:{*,slanted
why such a simple and elegant solution was
not around before…
they were to some extend (in split=text mode) but never advocated but we
added some to it as well as made it work with diferent alignments (most
noticeably slanted) and number placement (overflow)
As a plain TeX traditionalist I am
right.
You're joking right? SInce when can one not set up something in some
context subsystem? Why would I make a table mechanism with no presets?
\starttext
\setupxtable[suffix][align=middle,foregroundcolor=red]
\setupxtable[blabla][foregroundstyle=slanted]
\setupxtable[crap] [foregroundcolor
[learned][style=sansbold, textstyle=slanted, n=1,
pagenumber=yes]
\starttext
\learned{CCSS+W.7.3}
\input knuth
\learned{CCSS+W.7.3}
\input knuth
\learned{CCSS+W.7.1}
\startchapter[title=Standards]
\placelearned
\stopchapter
\stoptext
it creates a custom index entry, and `\placelearned` displays
that index.
\defineregister[learned][compress=yes]
\setupregister[learned][style=sansbold, textstyle=slanted, n=1, pagenumber=yes]
\starttext
\learned{CCSS+W.7.3}
\input knuth
\learned{CCSS+W.7.3}
\input knuth
the following code to
create such an index, if I simply place `\learned{}` somewhere containing the
standard's ID, it creates a custom index entry, and `\placelearned` displays
that index.
\defineregister[learned][compress=yes]
\setupregister[learned][style=sansbold, textstyle=slanted, n=1
Here is my minimum working example:
\defineregister[listdates][compress=yes]
\setupregister[listdates][style=sansbold, textstyle=slanted, n=1,
pagenumber=yes]
\define[2]\dateis{%
\listdates{#1~\emdash ~#2}%
}%
\starttext
\dateis{1900s+1911}{Some event happened}
\dateis{1900s+1912}{Yet an
tdates][compress=yes]
\setupregister[listdates][style=sansbold, textstyle=slanted, n=1,
pagenumber=yes]
\define[2]\dateis{%
\listdates{#1~\emdash ~#2}%
}%
\starttext
\dateis{1900s+1911}{Some event happened}
\dateis{1900s+1912}{Yet another event happened}
\dateis{1900s+1912}{Another event happ
with a Junicode fallback, lib-fb-jun
\definefontfallback[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
\starttypescript [serif] [lib-fb-jun]
\definefontsynonym [Libertine-Roman] [file:linlibertiner]
\definefontsynonym [Libertine-Slanted] [file:linlibertineri] % works fine
, lib-fb-jun
>
>
> \definefontfallback[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
>
> \starttypescript [serif] [lib-fb-jun]
>\definefontsynonym [Libertine-Roman] [file:linlibertiner]
>\definefontsynonym [Libertine-Slanted] [file:linlibertineri] % works f
ontfallback[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
>
> \starttypescript [serif] [lib-fb-jun]
> \definefontsynonym [Libertine-Roman] [file:linlibertiner]
> \definefontsynonym [Libertine-Slanted] [file:linlibertineri] % works
> fine
> \stoptypesc
[junicodefallback][name:Junicode][privateusearea][check=yes,force=no]
\starttypescript [serif] [lib-fb-jun]
\definefontsynonym [Libertine-Roman] [file:linlibertiner]
\definefontsynonym [Libertine-Slanted] [file:linlibertineri] % works fine
\stoptypescript
\starttypescript [serif] [lib-fb-jun] [name
,
force=yes]
\definefallbackfamily [nanum] [rm] [Noto Serif CJK KR]
[range={cjkunifiedideographs},force=yes]
\definefontfamily [nanum] [rm] [Nanum Myeongjo OTF]
[ it={style:regular,features:{*,slanted}},
bi={style:bold,features:{*,slanted}},force=yes]
Explanation:
1. I use Korean fo
(the \sc
column is the fallback style). \swapface is unchanged and I'm not sure about
its output because it uses the \em code for italic and slanted which means
\setupbodyfontenvironment[default][em=blue] affects also the \swapface results.
Thank you very much for attacking and clarifying
; Attached is the output from a modified version of the styling command (the
> \sc column is the fallback style). \swapface is unchanged and I'm not sure
> about its output because it uses the \em code for italic and slanted which
> means \setupbodyfontenvironment[default][em=blue] affects
for italic and
slanted which means \setupbodyfontenvironment[default][em=blue] affects
also the \swapface results.
Wolfgang
emphasis.pdf
Description: Adobe PDF document
___
If your question is of interest to others
report: \meaning\italicface gives:
protected macro:\relax \ifx \fontalternative \s!tf \it \orelse
\ifx \fontalternative
\s!bf \bi \else \tf \fi
This leaves out the transition from bi to bf. That transition is done
by \emph, but \emph may give slanted while \italicface is always italic
}: \type{\emIt
\definehighlight[style=italic]}
\stoptext
The \em command has two special values which are allowed when you
change the style with
\setupbodyfontenvironment[default][em=...]
with the value "slanted" and "italic". When you choose one of them
]}
\stoptext
The \em command has two special values which are allowed when you
change the style with
\setupbodyfontenvironment[default][em=...]
with the value "slanted" and "italic". When you choose one of them the
result depends on the current weight (\tf or \bf) but wit
are allowed when you change
the style with
\setupbodyfontenvironment[default][em=...]
with the value "slanted" and "italic". When you choose one of them the
result depends on the current weight (\tf or \bf) but with every other
value you're just using whatever the style c
On 6/23/2021 10:32 PM, Henning Hraban Ramm wrote:
Am 23.06.2021 um 21:42 schrieb Bruce Horrocks :
On 23 Jun 2021, at 07:43, Henning Hraban Ramm wrote:
You can combine whatever you like in one typescript, but you’re restricted to
six styles (regular, italic, slanted, bold, bold italic
> Am 23.06.2021 um 21:42 schrieb Bruce Horrocks :
>
>
>> On 23 Jun 2021, at 07:43, Henning Hraban Ramm wrote:
>>
>> You can combine whatever you like in one typescript, but you’re restricted
>> to six styles (regular, italic, slanted, bold, bold italic, bold
> On 23 Jun 2021, at 07:43, Henning Hraban Ramm wrote:
>
> You can combine whatever you like in one typescript, but you’re restricted to
> six styles (regular, italic, slanted, bold, bold italic, bold slanted). You
> can just “abuse” the italic or slanted styles for you
, italic, slanted, bold, bold italic, bold slanted). You can
just
“abuse” the italic or slanted styles for your other weights.
... or use roman styles, if you don’t need roman.
Thanks for your help.
After playing a bit more with the different variants for loading fonts it looks
like I don't even
hatever you like in one typescript, but you’re restricted
> > to
> six styles (regular, italic, slanted, bold, bold italic, bold slanted). You
> can just
> “abuse” the italic or slanted styles for your other weights.
>
> ... or use roman styles, if you don’t need roman.
Th
ular ExtraBold.)
>> Is my understanding of typescripts correct that I cannot have bold and
>> extrabold in the same typescript? And that I need a typescript for regular
>> and one for the semicondensed variants?
>
> You can combine whatever you like in one typescript, but you
d and
> extrabold in the same typescript? And that I need a typescript for regular
> and one for the semicondensed variants?
You can combine whatever you like in one typescript, but you’re restricted to
six styles (regular, italic, slanted, bold, bold italic, bold slanted). You can
just “abus
On 6/11/21 6:08 PM, Hans Hagen wrote:
> Hi,
>
> In addition the the mentioned integral trickery we can now do this
>
> \setupbodyfont[newcomputermodern-book]
Hi Hans,
many thanks for the new upload.
I’m afraid that now slanted for New Computer Modern Mono doesn’t work:
\m
]
[text=Définition,
number=no,
headcommand=\groupedcommand{}{},
style=slanted]
\setupmathematics[stylealternative=calligraphic]
\unexpanded\def\CScript#1#2{\start\switchtobodyfont[stixtwo]\m{{\mathscript{#1}}_{#2}}\stop}
\unexpanded\def\cscript#1{\start\switchtobodyfont[stixtwo]\m
tc. text
\starttext
\startlines
$\mathtexttf{upright text}$
$\mathtextit{italic text}$
$\mathtextsl{slanted text}$
$\mathtextbf{bold text}$
$\mathtextbi{bolditalic text}$
$\mathtextbs{boldslanted text}$
\stoplines
\startlines
$\mathwordtf{upright word}$
$\mathwordit{italic word}$
$\mat
,
background=color,
backgroundcolor=white,
]
%%%
\defineenumeration[proclaim]
[text=,
before={\starttextbackground[leftbartext]},
after={\stoptextbackground},
style=slanted,
title=yes,
titleleft=,
titleright
Sylvain Hubert schrieb am 08.11.2020 um 13:02:
On Sun, 8 Nov 2020 at 11:24, Pablo Rodriguez <mailto:oi...@gmx.es>> wrote:
Hi Sylvain,
this is the same as:
\definefontfamily[face1][rm][gabriola]
Just in case, "slanted" is an already defined feature. It
On Sun, 8 Nov 2020 at 11:24, Pablo Rodriguez wrote:
> Hi Sylvain,
>
> this is the same as:
>
> \definefontfamily[face1][rm][gabriola]
>
> Just in case, "slanted" is an already defined feature. It slants the font.
>
> > \definefontfamily[fa
]
Just in case, "slanted" is an already defined feature. It slants the font.
> \definefontfamily[face2][rm][gabriola][it={features:{default,
> effect={}}}]
> \definefontfamily[face3][rm][gabriola][it={features:{default,
> effect={width=1.0}}}]
BTW, the documentation is cl
hat special: it does automatic italic correction and changes the
> alternative depending on the current alternative. For example, if the
> current font alternative is normal (i.e. upright), \em switches to slanted;
> and if the current font alternative is slanted, \em switches to normal."
>
nding on the current alternative. For example, if the
current font alternative is normal (i.e. upright), \em switches to slanted;
and if the current font alternative is slanted, \em switches to normal."
And using \definebodyfontenvironment[default][em=italic] to use italic
instead of slanted; fo
, the built-in gyre bonum font doesn't have a slanted/oblique variant, so if
I have Bookman as my main body
font, \sl produces (unsurprisingly) the same result as \it,
TexGyreBonum-Italic. If I want \sl to summon
Latin Modern for the variant, I have tried variations on
\definetypeface [Bookman] [rm
ubstitute, works fine)
>> Now, the built-in gyre bonum font doesn't have a slanted/oblique variant, so
>> if I have Bookman as my main body
>> font, \sl produces (unsurprisingly) the same result as \it,
>> TexGyreBonum-Italic. If I want \sl to summon
>> Latin Modern
] [default]
\definetypeface [Bookman] [ss] [sans] [unitus] [default]
\definetypeface [Bookman] [mm] [math] [modern] [default]
(Unitus is the fontsite 500 'Univers' substitute, works fine)
Now, the built-in gyre bonum font doesn't have a slanted/oblique variant, so if
I have Bookman as my main body
font
] [unitus] [default]
\definetypeface [Bookman] [mm] [math] [modern] [default]
(Unitus is the fontsite 500 'Univers' substitute, works fine)
Now, the built-in gyre bonum font doesn't have a slanted/oblique variant, so if
I have Bookman as my main body
font, \sl produces (unsurprisingly) the same result
On 7/15/2020 5:03 PM, Pablo Rodriguez wrote:
Dear list,
I have the following sample:
\definefontfamily
[mainface]
[rm]
[TeX Gyre Pagella]
[it={style:regular, features:{default, slanted}},
bi={style:regular, features:{default, boldened, slanted
Dear list,
I have the following sample:
\definefontfamily
[mainface]
[rm]
[TeX Gyre Pagella]
[it={style:regular, features:{default, slanted}},
bi={style:regular, features:{default, boldened, slanted}},
bf={style:regular, features:{default
, I think (not that I need it, I only want the
ss form anyway).
This has still nothing to do with the serif/roman style,
what the setup does is to map the slanted and boldslanted
alternatives to the italic files. You can achieve the same
with two additional \definefontsynonym lines for &qu
]
\setupbodyfontenvironment[default] [em=italic]
Not necessary because Pagella has no slanted alternative and \sl uses
the italic alternative.
\setupdelimitedtext[blockquote][style=\tfx,
before={\blank\setupinterlinespace[line=2.4ex]},after={\blank}]
My publisher thinks the default scaling of 'x' (0.8) is too
the same prime character as in TeX/LaTeX? Or has
> something changed in latin modern? See the attached pdf files
> (derivatives.pdf from ConTeXt and primetime-crop.pdf from lualatex). The
> prime character looks more slanted in ConTeXt. It also almost looks like it
> is cut horizontally
from ConTeXt and primetime-crop.pdf from lualatex).
The prime character looks more slanted in ConTeXt. It also almost
looks like it is cut horizontally at the bottom of the character.
Also, the space between the two x in the subscript looks a bit large
to me. Is that easily tuned?
ConTeXt uses
} unless of course
> the index applies the second something
>
> But i bet that Aditya can give the real answer.
>
> Hans
>
> -
> Hans Hagen | PRAGMA ADE
>
I know that there are commands for
>> formatting index entries, like:
>>
>> \index{sl::īga}
>>
>> if I want the word 'īga' to be printed in slanted type. I also know that we
>> can create sub-entries, like
>>
>> \index{īga+emphasized}
>>
>> Bu
Robert Zydenbos schrieb am 21.08.2019 um 10:59:
Dear list members,
In my book I am creating an index. I know that there are commands for
formatting index entries, like:
\index{sl::īga}
if I want the word 'īga' to be printed in slanted type. I also know that we can
create sub-entries, like
Dear list members,
In my book I am creating an index. I know that there are commands for
formatting index entries, like:
\index{sl::īga}
if I want the word 'īga' to be printed in slanted type. I also know that we can
create sub-entries, like
\index{īga+emphasized}
But now I want the word
, and it outputs the definition of the internal \*section*
command, of which \section is an instance. (The parents of instances are
printed in a slanted font).
This is absolutely magic and extremely useful! Thank you, Wolfgang, Taco and
Hans!
I wonder whether the magic behind the scenes would
rent arguments, and it outputs the definition of the internal
> \*section* command, of which \section is an instance. (The parents of
> instances are printed in a slanted font).
This is absolutely magic and extremely useful! Thank you, Wolfgang, Taco and
Hans!
I wonder whether the magic behind th
.
Multiple tables actually, as it also outputs the alternative calls with
different arguments, and it outputs the definition of the internal \*section*
command, of which \section is an instance. (The parents of instances are
printed in a slanted font).
this is really great!
This gives idea what
of instances are
printed in a slanted font).
There are 2035 normal commands and 373 instances in the database, essentially
covering all the style- and document-level commands in ConTeXt.
I’ve decided not to add the low-level system commands because (apart from
perhaps a few special cases) these do
ust three words for correct hyphenation?
>
> \starttext
> English ... \language[de]{Deutsch}
> \stoptext
Shouldn’t that be
\starttext
English ... {\language[de]Deutsch}
\stoptext
?
For most languages you can also use their shortcut, e.g. \de, \ru, \en – but
not \it (itali
,
% topoffset=-2mm
]
\defineenumeration[proclaim]
[text=,
before={\startsidebar[ProclaimSidebar]},
after={\stopsidebar},
style=slanted,
title=yes,
titleleft=,
titleright={.},
% alternative=serried,
alternative=hanging
=\TitleFont,page=no]
\definehighlight[emph][style=italic]
\starttext
\chapter{My \emph{special} chapter} % no font change
\input tufte
\emph{\input knuth.tex }
\chapter{My {\em oldfashioned} chapter} % slanted body font
\input tufte
{\em\input knuth.tex }
\stoptext
-
Am 2019-01-22 um 19:57 schrieb
]
\setupbodyfont[11pt]
\defineregister [change]
\setupregister [change] [
indicator=no %% no letter
style=sansbold, %% headings
textstyle=slanted,%% entries
pagestyle=bolditalic, %% page refs
n=1, %% columns
]
\def\ChangeV#1#2{\change{#1+#2}\doifmode
On Fri, Dec 7, 2018 at 4:15 PM Alan Braslau wrote:
>
> On Fri, 7 Dec 2018 09:06:03 +0100
> "Mikael P. Sundqvist" wrote:
>
> > 2) Support for transforming images in a more general way. With the
> > zscaled, slanted, ... we are able to transform any object in a
On Fri, 7 Dec 2018 09:06:03 +0100
"Mikael P. Sundqvist" wrote:
> 2) Support for transforming images in a more general way. With the
> zscaled, slanted, ... we are able to transform any object in an affine
> way. It would be nice to be able to transform any object in a more
ut this a while ago and got a simple solution
working for that curve, but I think a general working solution would
be neat. I think the bernoulli lemniscate could be a good test curve,
since it intersect itself.
2) Support for transforming images in a more general way. With the
zscaled, slanted, .
1 - 100 of 599 matches
Mail list logo
